BUGFIXES.TXT

                      Bug Fixes for RASVBX version 1.34
				Version 1.33

                 Copyright (C) 1994 Cutting Edge Consulting.
                           All Rights Reserved.


This document contains a list of bug fixes for RASVBX version 1.34.
On-line information on properties and events is available in RASVBX.HLP.


BUG FIXES:
=========
(1.2)GP-Fault when RAS not installed.
      Version 1.20 fixed the bug that made VB applications GP-Fault 
      when launched from Pcs that did not have RAS installed.

(1.3)GP-Fault in RASAPI16.DLL.
      Version 1.30 fixed the bug that caused a General Protection
      Fault in RASAPI16.DLL when loading RasVBX more than once during
      a Windows session.  

(1.3)Invalid ConnectState property.
      In previous versions the ConnectState property returned -18xxx.
      This is because the return value was not defined when internal 
      errors occurred.  The ConnectState property now returns -1 if 
      there is an error.  Calls into RASAPI16.DLL were often returning
      NOT_ENOUGH_MEMORY errors.  When RASVBX gets these errors, it now 
      returns (1) to the VB application, assuming the reason for the 
      OUT_OF_MEMORY error is because of a remote connection.

(1.3)Cannot run on Windows NT.
      RASVBX previousy returned a "Remote Access is not properly 
      installed" error when attempting to run on Windows NT.  This
      was an oversight, but has been fixed.

(1.31)RASVBX always redials even when RedailAttempts is set to zero.
       Setting RedialAttemps to zero now prevents RASVBX from redialing
       in the event that the connection is dropped.  Setting this
       property to a positive integer greater than zero causes RASVBX
       to redial that many times before it stops trying.  A value of 3
       or 4 should be appropriate in most circumstances.

(1.31)RASVBX not unloading from memory.
       RASVBX version 1.31 did not unload completely from memory when 
       your application closed.  This may have caused GP Faults in 
       VBRUN300.DLL or RASAPI16.DLL when running more than one
       instance of your application in a single Windows session.
       This problem has been fixed and the comtrol now completely
       unloads from memory when your VB program ends.  (Be sure to
       include the keyword END in the unload of your Main Form.)

(1.32)DialEvent not firing at runtime.
       The DialEvent event was previously not being fired at runtime
       when the ShowConnection property was set to False.  This has 
       been fixed.

(1.33)The not installed message is displayed only if ShowErrors is set 
       to True.

(1.34)Fixes a problem in the implementation of the above.

KNOWN PROBLEM:
=============
There is a known bug in RASAPI16.DLL that prohibits multiple applications
from using RAS services simultaneously.  For this reason, a General 
Protection Fault occurrs when trying to use an application that uses
RasVBX and trying to use the Remote Access application that ships with
WFW.  Any thoughts?



Cutting Edge Consulting, Inc.
317 Bennington Hills 
W. Henrietta, NY  14586-9770

Phone: 716.425.2848